Saving an object to the Repository
There are different methods for saving objects to the Repository
|
To save an object to the Repository: |
- Click in the Repository object design window to make it the current AppBuilder design object.
- From the AppBuilder main window, choose File
Save, File Save Static Object as Dynamic, or File Save Dynamic Object as Static. - For Static object, type the filename as well as the extension you want to use to save the object to the file system, then choose OK. The AppBuilder saves a physical file in the file system for that object.
- You can also specify a custom super procedure to go with this dynamic object, or data logic procedures for SDOs and SBOs.
- Choose OK.
Save invokes the normal Save dialog box with options to let you register the object and specify deployment options, as shown:
See the "Saving a dynamic object as static" section for more information on this option.
If the object is an existing static Repository object, the object is saved back to the file system in the file from which you opened it.If the object is an existing static Repository object, the object is saved back to the file system in the file from which you opened it and the Repository is updated with the latest static file information.
When a static object is saved to the Repository, the whole object is not actually stored there. Only certain properties about the object are registered in the Repository, such as its name and object type. The actual source of the object is still saved to the file system in the location you specified. The location you specify to save a static object file, using the Save As dialog box, can be different from the default path for the object’s product module.